v2.2.0 Release Notes
Zadig v2.2.0 was released on February 25, 2024.
# Feature List
New Features
- Basic components fully support multi-replica deployment
- K8s YAML project version management supports manual version creation
- K8s Helm Chart project supports test environment Chart instantiation deployment
- Custom workflow deployment and image distribution tasks support selecting versions
- Custom workflow supports host deployment scenarios
- Custom workflow deployment tasks support execution in input order
- Custom workflow supports object storage cache
- Code scanning and testing support configuring the number of concurrent executions
- Windows build supports PowerShell scripts
- Release plan supports selecting versions
- Added code scanning template for template library
- OpenAPI adds new environments, services, project permissions, and users
Other Repairs and Optimizations
- Enhanced security of user and permission-related interfaces
- Interactive optimization of host project service configuration
- System announcement display page optimization
- Custom workflow blue-green release task resource cleanup logic optimization
- Fixed panic issues with Cron service in certain scenarios
- Product workflow is offline, and data is automatically migrated to custom workflow
# Business Change Statement
- The product workflow is offline, and the original product workflow data is automatically migrated to the custom workflow. Due to the change of the workflow engine, some functions have been adjusted, as follows:
- Original product workflow Jenkins build function is offline, and will be supported in custom workflows in the future
- Original product workflow webhook Update policy
动态选择空闲环境更新and设定指定环境为基准环境functions in the trigger are offline, and subsequently supported in custom workflows - The original product workflow mirror rollback function is temporarily offline, and will be supported in custom workflows in the future.
- If the environment is not specified in the original product workflow, an environment will be automatically selected to fill in after upgrading.
- k8s yaml Project creation version and version release function changes, please refer to the documentation for details
- The system is built-in variable adjustment, and you can use custom workflow variable transfer capabilities to obtain corresponding variables by adjusting configuration and scripts.
- Test
- Downline variables:
LINKED_ENV,ENV_NAME,SERVICES - Modify the change amount:
TEST_URLtoTASK_URL
- Downline variables:
- Build
- Downline variables:
DIST_DIR,ENV_NAME - Modify the change amount:
BUILD_URLtoTASK_URL
- Downline variables:
- Test
- The new workflow after migration is unified in view
所有
Warning
If the original product workflow itself cannot be executed normally, the workflow will not be automatically migrated to the custom workflow.
- The host access method is adjusted. In the v2.2.0 version, the same host only supports one access method. If SSH and agent are configured before upgrading, the system will automatically retain the SSH configuration after upgrading, and the Agent method needs to be re-connected after upgrading.
- The host project deployment configuration adjustment is no longer supported and built steps shared workspace. If there are files in the deployment task using the build task workspace, the configuration needs to be adjusted after upgrading.
# Version Upgrade Process
Warning
Due to the specificity of product workflow configuration and the risk of data upgrade failure, it is strongly recommended that product workflows be moved to custom workflows by themselves.
Warning
If you are using MongoDB Version > 4.0 and deployed in Replica Set mode, please confirm that the business library is not used admin/local/config/test supported to the system library Zadig ; if it is used, please manually migrate the data first. If the current system version is available < v2.1.0 please upgrade to v2.1.0 first. For the specific upgrade process, please refer to the v2.1.0 upgrade method , and then upgrade to v2.2.0
Please perform the corresponding upgrade process according to different installation methods:


